home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
TeX 1995 July
/
TeX CD-ROM July 1995 (Disc 1)(Walnut Creek)(1995).ISO
/
tex-k
/
tex-k-archive.past
/
1994.12.gz
/
1994.12
/
000070_kiril@uk_mailhost.sdrc.com_Tue Dec 20 54:39:39 1994.msg
< prev
next >
Wrap
Internet Message Format
|
1994-12-30
|
3KB
Received: from sdrc.com by cs.umb.edu with SMTP id AA29039
(5.65c/IDA-1.4.4 for <tex-k@cs.umb.edu>); Mon, 19 Dec 1994 10:00:10 -0500
Received: from uk_hawk (uk_mailhost.sdrc.com) by sdrc.com (4.1/SMI-4.1)
id AA23049; Mon, 19 Dec 94 09:44:52 EST
Received: by uk_hawk (AIX 3.2/UCB 5.64/4.03)
id AA19862; Mon, 19 Dec 1994 14:35:39 GMT
From: kiril@uk_mailhost.sdrc.com (Kiril Mitev)
Message-Id: <9412191435.AA19862@uk_hawk>
Subject: Re: prerelease testing
To: kb@cs.umb.edu (K. Berry)
Date: Mon, 19 Dec 1994 14:35:39 +22306404 (GMT)
Cc: tex-k@cs.umb.edu (!TeX chat )
In-Reply-To: <199412191130.AA13192@terminus.cs.umb.edu> from "K. Berry" at Dec 19, 94 06:30:59 am
X-Mailer: ELM [version 2.4 PL20]
Content-Type: text
Content-Length: 1736
Karl,
I would be happy to assist with HP-UX, although I can't promise
that the time lag between a release and a test would be short.
Whatever you define to be short.
My config is:
HP-UX 9.0? with the development environment, which incidentally
means an ANSI compiler.
I only use tex/xdvi/dvips, but I testing dvilj installation should
not be very different - I hope.
Cheers
Kiril Mitev
(and that's kiril.mitev@sdrc.com - do not REPLY to my mail)
>
> With this latest release, as with so many in the past, it seems there
> are a few problems that will strike people whose configuration differs
> in some aspect or another from mine.
>
> Generally, I only test the releases with GNU make and GCC, on the
> machines I have at home -- Ultrix, SunOS 4.1.3, and Linux (an old
> version). Sometimes also on HP-UX, Solaris 2.3, Alpha OSF/1 1.3, AIX
> 3.2.4, DG-UX 5.4.2, and IRIX 4.0.5. Also, I only test with the config.ps
> that we use at home.
>
> I'm thinking maybe it would be worthwhile to solicit a few volunteers to
> pretest releases on other configurations. That might help find problems
> early. I'm open to other suggestions, too, but I just don't want to
> spend any more time on testing myself, and I want to do *something*.
>
> Basically, pretesters would just have to retrieve the distribution to be
> tested from my machine, and configure/compile/test in the usual way,
> and, of course, be able to report and hopefully solve any problems.
>
> So, if you're interested, please send me mail saying what
> configuration(s) you're willing to test. As I imply above, testing with
> GCC and GNU make probably isn't terribly important, so if you use the
> vendor tools, that'd be particularly useful.
>
> kb@cs.umb.edu
>